What’s new
Org deployment
Share an app with another organization directly. Activity stays segmented per recipient. Updates flow automatically.
Collections sharing
Bundle a curated set of apps into a Collection and share it across many organizations. Update an app once, every recipient sees the new version.
App Insights
A new app-level view for builders. Set goals, track engagement, review individual conversations, see what’s working.
Permissions refresh
Apps start private. Editor and Viewer roles work per-app. Workspace toggles decide what members can build, see, and share.
What’s new for your role
Whether you build apps, run a class, admin an org, or deploy across a network, this release adds something for you.For builders
Your apps are yours from day one. New apps start private to you and your org’s admins. When you’re ready, share with a peer as Editor or Viewer through the Share modal. They get access to that one app, not your whole workspace. Change or revoke access at any time.For educators
You have more visibility into what students are doing and finer control over what they can do. Each workspace has three toggles for whether members can build apps, see each other’s work, or share apps beyond the workspace. The same app can live in multiple workspaces with activity segmented per class. A member detail page collects everything one student did inside the workspace.For administrators
Activity dashboards, flagged messages, and member detail pages live at the organization level. The question “what has this student been doing in Playlab” has a direct answer. Org admins see usage across every workspace from one dashboard, with filters by workspace, app, member, and date.For network owners
Share apps across multiple organizations through Collections. Build a curated set of apps once, share it with each partner, and updates flow automatically. Aggregate activity rolls up to you. Each partner sees only their own.A closer look at what’s new
Student data is more visible and accessible
You can segment activity on the same app by workspace, so each class sees only its own sessions. The member detail page collects everything a student did inside the workspace: apps used, conversations, flags, and apps built. A few patterns that work: Set a weekly review cadence. Open the Activity view every Friday and scan for sessions that stalled or members who haven’t engaged. Five minutes catches most issues. Use date filtering like last 7 days or last 14 days to avoid getting overwhelmed. Filter by flag status when you open the view. Anything flagged is worth a quick read. Open conversations that look unusual. A very long session for a brief assignment, or a very short session for a complex assignment, are signals worth investigating. Admins can see across classes. The org-level dashboard surfaces patterns no single workspace view would catch.Curate your favorite apps into a Collection and share across an organization
If you ship a set of apps to partners or districts, build a Collection once and share it. Recipients see updates as you publish them. Each district sees only its own activity, and you see aggregate usage across the network. Read the full guide →Apps can live in multiple workspaces; one update reaches all of them
Add the same app to as many workspaces as you need. Each class sees segmented activity. Update the app once, and every class using it sees the new version. Read the full guide →App-level and workspace-level control
New apps start private. You and your org’s admins can see them. You can add a peer as Editor or Viewer when you’re ready. They get access to that one app, not your whole workspace. You can change or revoke access at any time. For workspaces, three toggles decide whether members can build apps, see each other’s work, or share apps beyond the workspace. The settings can match how the class works.What’s changing in the structure
Playlab is now organized around four clear containers: organization, workspace, app, and collection. The container model gives you direct control over your apps, sharper boundaries between classes, and new ways to share what you build with the people you build for. Most of what you knew still works. The structure around it has shifted to give you more room to move. See how Playlab is organized → If you used Playlab before this update and want a workflow-by-workflow comparison, the What’s New section has migration guides, a side-by-side cheat sheet, and role-specific summaries of what changed.Coming soon
This summer we’re shipping deeper organization dashboards for cross-workspace member usage, expanded app insights with aggregated metrics, and rostering support. For the full list of what’s in flight, see Known limitations and what’s coming next.Learn with us
Join us at upcoming live sessions to see the new features in action and ask questions.Onboarding sessions
Live walkthroughs for new and returning users.
Office hours
Drop in with questions any week. We’re here.
Contact us
As you play with the new release, reach out any time at [email protected]. For deeper conversations, you’re always welcome at [office hours](/learn with us/office hours).Last updated: 06-01-2026 Contact us at [email protected]